Cookies or liberty enabler for processing all connections between user/agent and origin server in a wireless network for enabling cookies or liberty support services for users/agents

ABSTRACT

The invention provides a method and apparatus for enabling cookies-support services, liberty-support services, or a combination thereof, for particular clients, users and/or user agents in a wireless network. The method comprises the step of processing all connections between a client, user or user agent and an origin server through a cookies or liberty enabler to enable full user control over cookies or liberty acceptance and management for an end user. The cookies or liberty enabler may be arranged between the client, user or user agent and the origin server as either a component of a proxy/gateway or built into the origin server.

BACKGROUND OF THE INVENTION

[0001] 1. Field of Invention

[0002] The field of the invention lies in the field of supportingcookies and/or the liberty protocol on the server side whenever UAsupport is not available or not desirable.

[0003] 2. Description of Related Art

[0004] Recently, it has become possible for mobile terminals, such asmobile phones, personal digital assistance, etc., to access the Internetusing a Wireless Application Protocol (WAP), which is a communicationsprotocol and application environment for the deployment of informationresources, advanced telephony services and Internet access.

[0005] A cookie is a text file stored in memory of a device that hasbeen placed by a website on the Internet that was visited. In a typicalclient/server environment, a cookie allows the server side of theInternet connection to both store and retrieve information on the clientside. One advantage of cookies is that they can automatically identifythe client to the server, thereby shortening or eliminating the useridentification element of the log-in process. Moreover, a websitecontent provider can use a cookie to identify a particular websitepage(s) provided to a visitor based on the website provider's evaluationof user preferences during website visit(s) in relation to the cookie.The downside of cookies is that they are placed on the client devicewithout knowledge of the client, giving rise to concerns about privacythrough electronic trespass. Besides, the website content provider canuse information gathered about the client via cookies to steer and/ormodify the website access by the visitor/client based on these real orperceived user preferences.

[0006] Currently, there are two types of mobile phones on the market:those that support cookies, and those that do not. For phones thatsupport cookies, a client or user can select if they want to accept themor not. For phones that do not support cookies, a gateway typicallystores and accepts them for all users by default. However, this approachpresents a problem because cookies could be used for violating theprivacy of users and the gateway does not allow them any kind of choiceeven between enabling this service and disabling it. Another problem isthat the phone can support cookies, but their size could exceed the useragent (UA) capabilities to store them. In this case, the gateway may useits own storage to extend the usability of network services. Forexample, there is a known WAP gateway that has a special module thatalways accepts and stores cookies for user agents (UA) that do notsupport them. The component can be completely disabled, but that wouldaffect all users.

[0007] Similarly, the Liberty protocol standard is not widely availableduring Internet based access using WAP. Presently, there are only pilotimplementations of Liberty on the UA side. All UAs on the market do notsupport the Liberty standard. For instance, very few UAs have embeddedLiberty support. Most of the presently available UAs (over 99%) do nothave it. If the UA does not support the protocol, the service notavailable.

[0008] In view of the aforementioned, there is a need in the wirelessnetwork industry for providing cookies-support services, liberty-supportservices, or a combination thereof, at the discretion and control ofparticular clients, users and/or user agents in a wireless network.

SUMMARY OF INVENTION

[0009] In its broadest sense, the present invention provides a new andunique method and apparatus for enabling cookies-support services,liberty-support services, or a combination thereof, for particularclients, users and/or user agents in a wireless network. The methodcomprises the step of processing all connections between a client, useror user agent and an origin server through a cookies or liberty enablerto enable full user control over cookies or liberty acceptance andmanagement for an end user. The cookies or liberty enabler would bearranged between the client, user or user agent and the origin server aseither a component of a proxy/gateway or built into the origin server.

[0010] The invention provides a generic architecture for implementingthe handling of cookies and/or liberty protocol on the server side. Thisimplementation enables support for the cookies or the liberty securitymodel without the required support for them from the UA side.

[0011] The invention may take the form of a cookies or liberty enablerfor enabling cookies-support services, liberty-support services, or acombination thereof, for particular clients, users and/or user agents ina wireless network, wherein the cookies or liberty enabler processes allconnections between a client, user or user agent and an origin serverthrough the cookies or liberty enabler.

[0012] The invention may also take the form of a proxy/gateway forcoupling a client, user or user agent and an origin server in a wirelessnetwork, having a cookies or liberty enabler for enablingcookies-support services, liberty-support services, or a combinationthereof, for particular clients, users and/or user agents in thewireless network, wherein the cookies or liberty enabler processes allconnections between the client, user or user agent and the origin serverthrough the cookies or liberty enabler.

[0013] The invention may also take the form of an origin server forproviding content to a client, user or user agent in a wireless networkvia a proxy/gateway, having a cookies or liberty enabler for enablingcookies-support services, liberty-support services, or a combinationthereof, for particular clients, users and/or user agents in thewireless network, wherein the cookies or liberty enabler processes allconnections between the client, user or user agent and the origin serverthrough the cookies or liberty enabler.

[0014] The invention may also take the form of a wireless network havinga proxy/gateway for coupling a client, user or user agent to an originserver that provides content, having a cookies or liberty enablerarranged therein for enabling cookies-support services, liberty-supportservices, or a combination thereof, for particular clients, users and/oruser agents in the wireless network, wherein the cookies or libertyenabler processes all connections between the client, user or user agentand the origin server.

[0015] The invention may also take the form of a computer programproduct with a program code, which program code is stored on a machinereadable carrier, for carrying out the steps of the method when thecomputer program is run in a processing device in the cookies or libertyenabler.

BRIEF DESCRIPTION OF THE DRAWING

[0016] The drawing, not drawn to scale, includes the following Figures:

[0017]FIG. 1 is a diagram of wireless application protocol networkarchitecture.

[0018]FIG. 2A is a block diagram of a cookies enabler as a component ofa proxy/gateway in the network shown in FIG. 1.

[0019]FIG. 2B is a block diagram of a cookies enabler built into anorigin server in the network shown in FIG. 1.

[0020]FIG. 2C is a block diagram of the cookies enabler shown in FIGS.2A and 2B.

[0021]FIG. 2D is a block diagram of a server side cookies handlingalgorithm.

[0022]FIG. 3A is a block diagram of a liberty enabler as a component ofa proxy/gateway in the network shown in FIG. 1.

[0023]FIG. 3B is a block diagram of a liberty enabler built into anorigin server in the network shown in FIG. 1.

[0024]FIG. 3C is a block diagram of the liberty enabler shown in FIGS.3A and 3B.

[0025]FIG. 3D is a block diagram of a server side liberty (via cookies)handling algorithm.

[0026]FIG. 4A is a block diagram of a liberty enabler as a component ofa proxy/gateway in the network shown in FIG. 1.

[0027]FIG. 4B is a block diagram of a liberty enabler built into anorigin server in the network shown in FIG. 1.

[0028]FIG. 4C is a block diagram of the liberty enabler shown in FIGS.4A and 4B.

[0029]FIG. 4D is a block diagram of a server side liberty (via cookies)handling algorithm.

DETAILED DESCRIPTION OF INVENTION FIG. 1: WAP Network Architecture

[0030]FIG. 1 shows a wireless application protocol (WAP) networkarchitecture generally indicated as 10, consisting of a client, user oruser agent 12, a WAP gateway proxy 14 (also known as a proxy/gateway)and an origin server 16. Typically, the client 12, which may be in theform of a mobile phone, a personal digital assistant (PDA) or othermobile equipment, can access the Internet using the WAP protocol byproviding a Wireless Session Protocol (WSP) request with a UniversalResources Locator (URL) to the WAP gateway proxy 14 via wirelesscommunication. The WAP gateway proxy 14 processes the WSP request andprovides a Hypertext Transfer Protocol (HTTP) request to the originserver 16 via the Internet. In response to the HTTP request, the originserver 16 provides an HTTP response with content back to the WAP gatewayproxy 14 via the Internet. The WAP gateway proxy 14 receives the HTTPresponse and provides a WSP response to the client 12 with the content.

[0031] The invention provides a new and unique method and apparatus forenabling cookies-support services, liberty-support services, or acombination thereof, for particular clients, users and/or user agents 12in the network shown in FIG. 1. The method comprises the step ofprocessing all connections between the client, user or user agent 12 andthe origin server 16 through a cookies or liberty enabler shown anddescribed in detail below to enable full user control over cookies orliberty acceptance and management for an end user, such as the client12. The cookies or liberty enabler may be arranged between the client,user or user agent 12 and the origin server 16 as either a component ofthe gateway proxy 14 or built into the origin server 16 in FIG. 1. Thesteps of the method may be implemented via a computer program running ina processing device in the cookies or liberty enabler.

FIGS. 2A-2D: The Cookies Enabler

[0032]FIGS. 2A and 2B show a cookies enabler 20 for enablingcookies-support services for particular clients, users and/or useragents 12 in the wireless network 10 shown in FIG. 1. The UA 12 does nottypically have to have cookies support. The cookies enabler 20 processesall connections between the client, user or user agent (UA) and theorigin server 16 through the cookies enabler 20 and enables full usercontrol over cookies acceptance and management for an end user 12. Theorigin server 16 is a facility that provides content and consumes orproduces cookies and does not have to be aware of cookies support in UAside.

[0033]FIG. 2A shows the cookies enabler 20 implemented in theproxy/gateway 14 for coupling the client, user or user agent 12 and theorigin server 16 in the wireless network 10 shown in FIG. 1.

[0034]FIG. 2B shows the cookies enabler 20 implemented in the originserver 16 which has a server 16′ for providing content to the client,user or user agent 12 in the wireless network 10 shown in FIG. 1 via theproxy/gateway 14.

FIG. 2C: The Cookies Enabler

[0035]FIG. 2C shows a diagram of the cookies enabler 20 having a cookiesenabler processor 20 a for coordinating a cookies message generator 20b, a UA-specific cookies database 20 c, a cookies enabler core 20 d, acookies management front end 20 e and a cookies enabler input/output 20f. The cookies enabler core 20 d performs the main cookies enablerfunctions in relation to the client, user or user agent 12 and theorigin server 16 consistent with that discussed below with regard toFIG. 2D. The cookies repository or database 20 c is responsible not onlyfor storing the cookies, but also for maintaining user preference. Thecookies message generator 20 b provides cookies messaging functionalityin relation to the client, user or user agent 12 and the origin server16. The cookies management front end 20 e provides an interface thatallows the user to log in and check his stored cookies and manage themand other relevant cookies settings. The cookies enabler input/output 20f performs the input/output functionality in relation to the client,user or user agent 12 and the origin server 16.

[0036] The cookies message generator 20 b, UA-specific cookies database20 c, cookies enabler core 20 d, cookies management front end 20 e andcookies enabler input/output 20 f may be implemented using hardware,software, or a combination thereof. The scope of the invention is notintended to be limited to any particular implementation thereof. Forexample, a typical software implementation may include using amicroprocessor architecture having a microprocessor, a random accessmemory (RAM), a read only memory (ROM), an input/out devices and acontrol, address and databus for connecting the same.

FIG. 2D: Server Side Cookie Handling Algorithm

[0037]FIG. 2D shows a block diagram of a cookies handling algorithmhaving steps which are discussed below:

[0038] As shown, upon receiving a request for a universal resourcelocator (URL) from the client, user or user agent 12, the cookiesenabler core 20 d checks if there is support of the cookies protocol forthe client, user or user agent 12 and if the domain is enabled.

[0039] The cookies enabler core 20 d also fetches cookies from thecookies repository 20 c and forwards the request with cookies fetched,if any, to the origin server 16.

[0040] After receiving a response from the origin server 16 with cookies(or without), the cookies enabler core 20 d checks if cookies werereturned from the origin server 16 and that the cookies protocol is notdisabled for the domain. The cookies enabler core 20 d then sends theresponse received from the origin server 16 to the client, user or useragent 12, and stores the cookies, if any, in the cookie repository 20 c.

[0041] Moreover, the cookies enabler core 20 d can checks if the domainis not authorized to always accept cookies and sends the client, user oruser agent 12 a generated warning page with one or more cookies acceptoptions, including cookies accept options such as “accept,” “reject,”“always accept,” “always reject”, or a combination thereof. The client,user or user agent 12 may choose the one or more cookies accept optionsand forwards a decision to the cookies enabler core 20 d, which storesthe cookies if the cookies are accepted by the client, user or useragent 12, as well as storing user preferences in the cookies repository20 c if the cookies are accepted by the client, user or user agent 12and the acceptance is a persistent acceptance, such as “always accept”or “always reject”.

[0042] By way of example, the cookies enabler core 20 d and the messagegenerator 20 b may be a component of a WAP Gateway, while the UA cookiesdatabase 20 c may be deployed in a profile server. For the cookiesmanagement front end 20 e, any web server may be used that supportsscripting or module extensions.

FIGS. 3A-3D: Liberty Enabler

[0043]FIGS. 3A and 3B show a liberty enabler generally indicated as 30for enabling liberty-support services for particular clients, usersand/or user agents in the wireless network 10 shown in FIG. 1. Theliberty enabler 30 processes all connections between a client, user oruser agent 12 and the origin server 16 and enables full user controlover liberty acceptance and management for an end user 12.

[0044]FIG. 3A shows the liberty enabler 30 implemented in theproxy/gateway 14 for coupling the client, user or user agent 12 and theorigin server 16 as well as an identification (ID) provider 18 in thewireless network 10 shown in FIG. 1.

[0045]FIG. 3B shows the liberty enabler 30 implemented in the originserver 16 having a server 16′ for providing content to the client, useror user agent 12 in the wireless network 10 shown in FIG. 1 via theproxy/gateway 14. Similar to FIG. 3A, the liberty enabler 30 is alsocoupled to the identification (ID) provider 18.

FIG. 3C: Liberty Enabler

[0046]FIG. 3C shows a diagram of the liberty enabler 30 having a libertyenabler processor 30 a for coordinating a message generator 30 b, aUA-specific account database 30 c, a liberty enabler core 30 d, aaccount management front end 30 e and a liberty enabler input/output 30f.

[0047] The liberty repository or database 30 c would not only beresponsible for storing the names and passwords, but also formaintaining other relevant account settings.

[0048] Moreover, the account management front end 30 e provides aninterface that allows the user to log in and check his stored accountnames and passwords and manage them and the other relevant accountsettings.

[0049] The message generator 30 b, UA-specific account database 30 c,liberty enabler core 30 d, account management front end 30 e and libertyenabler input/output 30 f may be implemented using hardware, software,or a combination thereof. The scope of the invention is not intended tobe limited to any particular implementation thereof. For example, atypical software implementation may include using a microprocessorarchitecture having a microprocessor, a random access memory (RAM), aread only memory (ROM), an input/out devices and a control, address anddatabus for connecting the same.

[0050] The liberty enabler core 30 d with the message generator 30 bcould be a component of, for example, a WAP Gateway, while the UAaccount database could be deployed in, for example, a profile server.For the cookies management front end 20 e, any web server can be usedthat supports scripting or module extensions.

FIG. 3D: Server Side Liberty Handling Algorithm

[0051]FIG. 3D shows a block diagram of a liberty handling algorithmhaving steps which are discussed below:

[0052] As shown, upon receiving a request for a universal resourcelocator (URL) from the client, user or user agent 12, the libertyenabler core 30 d checks if there is support of the liberty protocol forthe client, user or user agent 12 and if he domain is enabled.

[0053] The liberty enabler core 30 d also fetches a libertyidentification (ID) from the account repository 30 c, which sends to theliberty enabler core 30 d a last liberty identification (ID) for thedomain, if available.

[0054] The liberty enabler core 30 d forwards the request with theliberty identification (ID), if available, to the origin server 16.

[0055] The liberty enabler core 30 d receives return content from theorigin server 16 if authorization is not required or the libertyidentification (ID) was valid and provides the return content to theclient, user or user agent 12.

[0056] The liberty enabler core 30 d may also receive a request forauthorization from the origin server 16 and ask the client, user or useragent 12 for a client or user name and password. In this case, theliberty enabler core 30 d may receive the user name and password fromthe client, user or user agent 12 and send to the identificationprovider 18 the user name and password associated with the client, useror user agent 12. Moreover, the liberty enabler core 30 d may receive anindication from the client, user or user agent 12 if the user name andpassword should be stored.

[0057] After receiving the name and password associated with the client,user or user agent from the identification provider 18, the libertyenabler core 30 d forwards the request with a liberty identification(ID) to the origin server 16. The liberty enabler core 30 d may alsostore the liberty identification (ID) if the client, user or user agentrequested the same.

[0058] After receiving return content from the origin server 16, theliberty enabler core 30 d provides the return content to the client,user or user agent 12.

FIGS. 4A-4D: Liberty Enabler (via Cookies)

[0059]FIGS. 4A and 4B show a liberty enabler (via cookies) generallyindicated as 40 for enabling liberty-support services for particularclients, users and/or user agents in the wireless network 10 shown inFIG. 1. The liberty enabler (via cookies) 40 processes all connectionsbetween a client, user or user agent 12 and the origin server 16 andenables full user control over liberty acceptance and management for anend user 12.

[0060]FIG. 4A shows the liberty enabler (via cookies) 40 implemented inthe proxy/gateway 14 for coupling the client, user or user agent 12 andthe origin server 16 as well as the identification (ID) provider 18 inthe wireless network 10 shown in FIG. 1.

[0061]FIG. 4B shows the liberty enabler (via cookies) 40 implemented inthe origin server 16 for providing content to the client, user or useragent 12 in the wireless network 10 shown in FIG. 1 via theproxy/gateway 14. Similar to FIG. 4A, the liberty enabler (via cookies)40 is also coupled to the identification (ID) provider 18.

FIG. 4C: Liberty Enabler (via Cookies)

[0062]FIG. 4C shows a diagram of the liberty enabler (via cookies) 40having a liberty enabler processor 40 a for coordinating a messagegenerator 40 b, a UA-specific account database 40 c, a liberty enablercore (via cookies) 40 d, an account management front end 40 e and aliberty enabler input/output 40 f.

[0063] The functionality of the liberty enabler processor 40 a and themessage generator 40 b is consistent with that discussed above. Theliberty repository or database 40 c would not only be responsible forstoring the names and passwords, but also for maintaining other relevantaccount settings. The functionality of the liberty enabler core (viacookies) 40 d is discussed below to the extent it differs from thefunctionality of the liberty enabler core 30 d discussed above. Theaccount management front end 40 e provides an interface that allows theuser to log in and check his stored account names and passwords andmanage them and the other relevant account settings. The functionalityof the liberty enabler input/output device 40 f is consistent with thatdiscussed above.

[0064] The message generator 40 b, UA-specific account database 40 c,liberty enabler core (via cookies) 40 d, account management front end 40e and liberty enabler input/output 40 f may be implemented usinghardware, software, or a combination thereof. The scope of the inventionis not intended to be limited to any particular implementation thereof.For example, a typical software implementation may include using amicroprocessor architecture having a microprocessor, a random accessmemory (RAM), a read only memory (ROM), an input/out devices and acontrol, address and databus for connecting the same.

FIG. 4D: Server Side Liberty (via Cookie) Handling Algorithm

[0065]FIG. 4D shows a block diagram of a liberty (via cookies) handlingalgorithm having steps which are discussed below:

[0066] Only the steps that are different from that shown in FIG. 3D willbe discussed below.

[0067] In FIG. 4D, the liberty enabler core 40 d checks if there is acookie with a liberty identification (ID) set, removes the cookie,extends the request, and forwards the request to the origin server 16.

[0068] After receiving return content from the origin server 16, theliberty enabler core 40 d provides the return content to the client,user or user agent 12 with the liberty identification (ID) in cookiesand stores the identification (ID) if the client, user or user agent 12chooses to store the same.

Scope of the Invention

[0069] Accordingly, the invention comprises the features ofconstruction, combination of elements, and arrangement of parts whichwill be exemplified in the construction hereinafter set forth.

[0070] It will thus be seen that the objects set forth above, and thosemade apparent from the preceding description, are efficiently attainedand, since certain changes may be made in the above construction withoutdeparting from the scope of the invention, it is intended that allmatter contained in the above description or shown in the accompanyingdrawing shall be interpreted as illustrative and not in a limitingsense.

I claim:
 1. A method for enabling cookies-support services,liberty-support services, or a combination thereof, for particularclients, users and/or user agents in a wireless network, characterizedin that the method comprises the step of processing all connectionsbetween a client, user or user agent and an origin server through acookies or liberty enabler.
 2. A method according to claim 1, whereinthe method comprises the step of processing enables full user controlover cookies or liberty acceptance and management for an end user.
 3. Amethod according to claim 1, wherein the method further comprises thestep of arranging the cookies or liberty enabler between the client,user or user agent and the origin server.
 4. A method according to claim3, wherein the step of arranging further comprises arranging the cookiesor liberty enabler as a component of a proxy/gateway.
 5. A methodaccording to claim 3, wherein the step of arranging further comprisesbuilding the cookies or liberty enabler into the origin server.
 6. Amethod according to claim 1, wherein the method comprises the step ofchecking if support of the cookies protocol for the client, user or useragent and domain is enabled upon receiving a request for a universalresource locator (URL) from the client, user or user agent.
 7. A methodaccording to claim 6, wherein the method comprises the step of fetchingcookies from a cookies repository in the cookie enabler.
 8. A methodaccording to claim 7, wherein the method comprises the step offorwarding the request with cookies fetched, if any, to the originserver.
 9. A method according to claim 6, wherein the method comprisesthe step of checking if cookies were returned from the origin server andthat the cookies protocol is not disabled for the domain upon receivinga response from the origin server.
 10. A method according to claim 9,wherein the method comprises the step of sending the response receivedfrom the origin server to the client, user or user agent.
 11. A methodaccording to claim 9, wherein the method comprises the step of storingthe cookies, if any, in a cookies repository.
 12. A method according toclaim 6, wherein the method comprises the step of checking if the domainis not authorized to always accept cookies.
 13. A method according toclaim 12, wherein the method comprises the step of sending the client,user or user agent a generated warning page with one or more cookiesaccept options.
 14. A method according to claim 13, wherein the step ofsending includes sending the one or more cookies accept options thatincludes: “accept,” “reject,” “always accept,” “always reject”, or acombination thereof.
 15. A method according to claim 13, wherein themethod comprises the step of allowing the client, user or user agent tochoose the one or more cookies accept options
 16. A method according toclaim 15, wherein the method comprises the step of storing the cookiesif the cookies are accepted by the client, user or user agent.
 17. Amethod according to claim 15, wherein the method comprises the step ofstoring user preferences in the cookies repository if the cookies areaccepted by the client, user or user agent and the acceptance is apersistent acceptance, such as “always accept” or “always reject”.
 18. Amethod according to claim 1, wherein the method comprises the step ofallowing the user to log in and check their stored cookies and managetheir stored cookies and other relevant cookies settings.
 19. A methodaccording to claim 1, wherein the method comprises the step of checkingif support of the liberty protocol for the client, user or user agentand domain is enabled upon receiving a request for a universal resourcelocator (URL) from the client, user or user agent.
 20. A methodaccording to claim 19, wherein the method comprises the step of fetchinga liberty identification (ID) from an account repository in the libertyenabler.
 21. A method according to claim 20, wherein the methodcomprises the step of sending from the account repository to the libertyenabler core a last liberty identification (ID) for the domain, ifavailable.
 22. A method according to claim 21, wherein the methodcomprises the step of forwarding the request with the libertyidentification (ID), if available, to the origin server.
 23. A methodaccording to claim 22, wherein the method comprises the steps ofreceiving return content from the origin server if authorization is notrequired or the liberty identification (ID) was valid and providing thereturn content to the client, user or user agent.
 24. A method accordingto claim 22, wherein the method comprises the step of receiving arequest for authorization from the origin server and asking the client,user or user agent for a client or user name and password.
 25. A methodaccording to claim 24, wherein the method comprises the step ofreceiving the user name and password from the client, user or useragent.
 26. A method according to claim 25, wherein the method comprisesthe step of receiving an indication from the client, user or user agentif the user name and password should be stored.
 27. A method accordingto claim 25, wherein the method comprises the step of sending to anidentification provider the user name and password associated with theclient, user or user agent.
 28. A method according to claim 27, whereinthe method comprises the steps of receiving the name and passwordassociated with the client, user or user agent from the identificationprovider and forwarding the request with a liberty identification (ID)to the origin server.
 29. A method according to claim 27, wherein themethod comprises the steps of storing the liberty identification (ID) ifthe client, user or user agent requested the same.
 30. A methodaccording to claim 28, wherein the method comprises the step ofreceiving return content from the origin server and providing the returncontent to the client, user or user agent.
 31. A method according toclaim 1, wherein the method comprises the step of allowing the user tolog in and check their stored account names and passwords and manage thesame and other relevant account settings.
 32. A method according toclaim 1, wherein the method comprises the step of checking if there is acookie with a liberty identification (ID) set, removing the cookie,extending the request, and forwarding the request to the origin server.33. A method according to claim 32, wherein the method comprises thestep of receiving return content from the origin server and providingthe return content to the client, user or user agent with the libertyidentification (ID) in cookies if the client, user or user agent choosesto store the information.
 34. A cookies or liberty enabler for enablingcookies-support services, liberty-support services, or a combinationthereof, for particular clients, users and/or user agents in a wirelessnetwork, characterized in that the cookies or liberty enabler comprises:a cookies or liberty enabler core for processing all connections betweena client, user or user agent and an origin server through the cookies orliberty enabler.
 35. A cookies or liberty enabler according to claim 34,wherein the cookies or liberty enabler core enables full user controlover cookies or liberty acceptance and management for an end user.
 36. Aproxy/gateway for coupling a client, user or user agent and an originserver in a wireless network, having a cookies or liberty enabler forenabling cookies-support services, liberty-support services, or acombination thereof, for particular clients, users and/or user agents inthe wireless network, characterized in that the cookies or libertyenabler comprises: a cookies or liberty enabler core for processing allconnections between the client, user or user agent and the origin serverthrough the cookies or liberty enabler.
 37. A proxy/gateway cookies orliberty enabler according to claim 36, wherein the cookies or libertyenabler core enables full user control over cookies or libertyacceptance and management for an end user.
 38. An origin server forproviding content to a client, user or user agent in a wireless networkvia a proxy/gateway, having a cookies or liberty enabler for enablingcookies-support services, liberty-support services, or a combinationthereof, for particular clients, users and/or user agents in thewireless network, characterized in that the cookies or liberty enablercomprises: a cookies or liberty enabler core for processing allconnections between the client, user or user agent and the origin serverthrough the cookies or liberty enabler.
 39. An origin server accordingto claim 40, wherein the cookies or liberty enabler core enables fulluser control over cookies or liberty acceptance and management for anend user.
 40. A wireless network having a proxy/gateway for coupling aclient, user or user agent to an origin server that provides content,having a cookies or liberty enabler arranged therein for enablingcookies-support services, liberty-support services, or a combinationthereof, for particular clients, users and/or user agents in thewireless network, characterized in that the cookies or liberty enablerprocesses all connections between the client, user or user agent and theorigin server.
 41. A wireless network according to claim 40, wherein thecookies or liberty enabler enables full user control over cookies orliberty acceptance and management for an end user.
 42. A wirelessnetwork according to claim 40, wherein the cookies or liberty enabler isarranged between the client, user or user agent and the origin server.43. A wireless network according to claim 40, wherein the cookies orliberty enabler is a component of the proxy/gateway.
 44. A wirelessnetwork according to claim 40, wherein the cookies or liberty enabler isbuilt into the origin server.
 45. A method according to claim 1, whereinthe method further comprises implementing the step of the method via acomputer program running in a processing means in the cookies or libertyenabler.
 46. A computer program product with a program code, whichprogram code is stored on a machine readable carrier, for carrying outthe steps according to claim 1 when said computer program is run in aprocessing means in the cookies or liberty enabler.